v1.69.0

Compare Source

• Increase check plugin WASM memory limits to 1GiB.
• Fix LSP stale diagnostics persisting after a file is closed or deleted.
• Fix handling of unprefixed newlines in block comments.
• Add LSP code lenses for buf.gen.yaml files: "Run buf generate" and "Check for plugin updates".
• Add LSP warnings for lint.ignore and breaking.ignore paths in buf.yaml that do not match any file in the workspace.

v0.45.0: 0.45.0

Compare Source

Enhancements

• Add support for forwarding free arguments via $POE_EXTRA_ARGS by @​timrid in #​380

Fixes

• Handle cancelled tasks correctly by @​timrid in #​378
• Preserve quotes in :+/:- operator arguments (#​333) by @​nat-n in #​377
• Handle ctrl+c attempt on windows if running bat/cmd scripts by @​NSPC911 in #​382

New Contributors

• @​timrid made their first contribution in #​378

Full Changelog: nat-n/poethepoet@v0.44.0...v0.45.0

v0.10.2

Compare Source

What's Changed

🚀 New Features

• Add references support for Cargo and pyproject workspaces by @​ya7010 in #​1821

🐛 Bug Fixes

• fix(lsp): resolve type definitions for scalar bindings by @​ya7010 in #​1820
• fix(vscode): allow spaced toml fences by @​ya7010 in #​1816

🛠️ Other Changes

• fix(pyproject): link build-system requires by @​ya7010 in #​1822
• feat(vscode): add TOML configuration defaults by @​ya7010 in #​1818
• Deprecate path declaration navigation in pyproject and cargo by @​ya7010 in #​1823
• Improve docs tables and workspace goto navigation by @​ya7010 in #​1825

Full Changelog: tombi-toml/tombi@v0.10.1...v0.10.2

v0.10.1

Compare Source

What's Changed

🚀 New Features

• Fix tombi config path resolution and completions by @​ya7010 in #​1807

🐛 Bug Fixes

• fix: keep root hover range on the current key-value by @​ya7010 in #​1812
• fix(config): reject empty schema glob patterns by @​ya7010 in #​1814

🛠️ Other Changes

• Add schema exclude support by @​ya7010 in #​1813
• docs: refine formatter intro wording by @​ya7010 in #​1815

Full Changelog: tombi-toml/tombi@v0.10.0...v0.10.1

v0.10.0

Compare Source

What's Changed

The file path specification in .config/tombi.toml has been modified to be searched starting from its parent directory, rather than from .config/.

🚨 Breaking Changes

• fix: add leading comment handling for empty tables and arrays in formatting by @​ya7010 in #​1800
• fix: resolve project-root paths from .config/tombi.toml config by @​ya7010 in #​1802

🐛 Bug Fixes

• fix: resolve schema paths from config base dir by @​ya7010 in #​1806

🛠️ Other Changes

• fix: remove redundant explanation for group-blank-lines-limit and table-blank-lines by @​ya7010 in #​1799
• Strengthen README overview by @​ya7010 in #​1801
• docs: correct terminology for auto sorting in documentation by @​ya7010 in #​1805
• ci: cache TOMBI_CACHE_HOME in CI by @​ya7010 in #​1804
• Add schema catalog path examples by @​ya7010 in #​1803

Full Changelog: tombi-toml/tombi@v0.9.26...v0.10.0

v0.9.26

Compare Source

What's Changed

🚀 New Features

• feat: add example paths for schema in JSON and Rust definitions by @​ya7010 in #​1798
• feat(formatter): add blank line spacing options by @​ya7010 in #​1792

🐛 Bug Fixes

• fix(vscode): enable markdown TOML fence injection by @​ya7010 in #​1794
• chore: update codeblock rule by @​ya7010 in #​1797

🛠️ Other Changes

• fix: update latest stable version to 0.9.25 in install script by @​ya7010 in #​1788
• fix(vscode): broaden markdown TOML fence matching by @​ya7010 in #​1790
• chore: update tombi.toml by @​ya7010 in #​1791
• fix(vscode): set formatter in workspace file by @​ya7010 in #​1795
• Update readme by @​ya7010 in #​1796

Full Changelog: tombi-toml/tombi@v0.9.25...v0.9.26

v0.9.25

Compare Source

What's Changed

🚀 New Features

• feat(vscode): highlight TOML front matter in Markdown by @​ya7010 in #​1782
• feat: update TOML formatter settings to include show_edit_predictions option by @​ya7010 in #​1783
• fix(zed): refine CLI bootstrap resolution order by @​ya7010 in #​1785

🛠️ Other Changes

• docs: update install.sh stable version to 0.9.23 by @​ya7010 in #​1778
• docs: update install.sh stable version to 0.9.24 by @​ya7010 in #​1779
• feat: Use app token for version update by @​ya7010 in #​1780
• chore: bootstrap Claude Code and Codex agent configuration by @​ya7010 in #​1781
• docs: document Zed edit predictions workaround by @​ya7010 in #​1784
• Remove simplify step from github-pr-flow by @​ya7010 in #​1786
• zed-v0.2.4 by @​ya7010 in #​1787

Full Changelog: tombi-toml/tombi@v0.9.24...v0.9.25

v0.0.39: 0.0.39

Compare Source

Summary

This version fixes several bugs related to link validation and lightbox configuration.

Changelog

Bug fixes

• fe42fc4 compat – shim for MkDocs validation syntax overrides Zensical's (#​607)
• acc2620 zensical – validation doesn't correctly map percent-encoded links (#​598)
• da317bf compat – add $...$ and $$...$$ blocks to exclusions for link validation (#​599)
• 94f0d29 zensical – anchor not extracted from combined anchor-text-fragment
• 273dd23 compat – auto-themed gallery takes precedence over explicit grouping
• c050add compat – error when setting caption_position on glightbox extension (#​604)
• 699d3be zensical – add Python backtrace on Markdown rendering error

Refactorings

• 3e27d69 compat – move glightbox config options to dataclass

v0.0.38: 0.0.38

Compare Source

Summary

This version adds link and footnote validation and strict mode – two of the most frequently requested features. Zensical now checks all internal references at build time and reports issues with precise source locations, so broken links don't make it into your published documentation. Unlike MkDocs, which only validates final rendered links, Zensical also checks for unresolved references, as well as unused and shadowed definitions – covering the full lifecycle of a reference from definition to use.

Validation

Zensical scans every Markdown file in your project and resolves all internal references against each other: inline links, reference-style links, footnotes, link definitions, and anchor targets. Every check is individually configurable and enabled by default.

$ zensical build
...
Warning: page does not exist
   ╭─[ index.md:3:14 ]
   │
 3 │ [id]: non-existent.md
   │       ───────┬───────
   │              ╰───────── page does not exist
───╯

The following checks for links and footnotes are now available:

• unresolved_references
• unresolved_footnotes
• unused_definitions
• unused_footnotes
• shadowed_definitions
• shadowed_footnotes
• invalid_links
• invalid_link_anchors

Strict mode

The new --strict command line flag causes the build to fail when any enabled validation check triggers, turning warnings into errors. This is useful for CI pipelines where you want to enforce link integrity and prevent broken documentation from being published:

$ zensical build --strict
...
Warning: unresolved link reference
   ╭─[ index.md:1:35 ]
   │
 1 │ This is an [unresolved reference][id].
   │                                   ─┬
   │                                    ╰── unresolved link reference
───╯
1 issue found
Aborted because --strict flag is set

Upgrading

No changes to your configuration are required – all checks are enabled by default. It's quite likely that you'll run into at least some warnings – as we did – when upgrading, since before, it was easy to miss unused link definitions or unresolved references. If you want to disable validation entirely, you can use:

[project]
validation = false

As always, if you run into any problems, please open an issue.

Changelog

Features

• 201c615 zensical, compat – add link and footnote validation and --strict mode (#​175)

Refactorings

• b3c1d91 zensical, compat – add custom Markdown subclasses
• ce8cbf8 zensical – simplify function definitions after zrx upgrade

v0.0.37: 0.0.37

Compare Source

Summary

This version adds support for installable themes. You can now bundle your theme overrides and package them into a custom theme which can be installed via pip.

As of now, we closely mirror the process used by MkDocs, where themes just need to register themselves in the mkdocs.themes entrypoint, to allow users that already have derivations of Material for MkDocs to run them on Zensical. In the coming months, with the advent of the component system, we'll make this process much more flexible and foster reuse at the component level. For now, this is a first step to allow sharing of theme overrides and default configurations inside organizations with dozens or even thousands of projects.

[!TIP]

If your organization has been a happy user of Material for MkDocs and is considering switching to Zensical, please support our work through Zensical Spark. Your financial contribution helps us achieve full compatibility with MkDocs much faster, gives you access to hands-on support by the core team, and allows you to shape Zensical together with us.

Changelog

Features

• 7694535 zensical, compat – installable theme extensions (#​511)

Bug fixes

• 72ba122 compat – sanitize nested metadata (#​582)
• 2fb663e compat – text adjacent to image included in link to open image in lightbox (#​579)
• dc32baf compat – anchor links preserved in table of content section titles (#​578)
• 127648e compat – attributes not applied to lightbox images

Refactorings

• 9872092 compat – subclass Markdown processors to extend functionality
• fdeb061 compat – use identical name for tree- and post-processor